home *** CD-ROM | disk | FTP | other *** search
- Im using Trumpet Winsock 1.0 Rev A to connect via 14.4k modem to a slip-server.
- The server needs a BOOTP request to send winsock the name server,
- network gateway and other info. The only way i have found it to work is to
- go into slip mode, go to the setup and type bootp in the I.P. address and then
- close Winsock, and then open Winsock back up. I have two problems with this:
- 1. My modem will hang up if i close WINSOCK, unless i issue the at&d0 command b
- efore making the server connection.
- 2. If I leave BOOTP in the I.P. address block when i want to start winsock
- up again, then it will pause and say unable to load TCP.
-
- Why do i have to go back and change bootp everytime I want to use it again?
- Isnt there a better way?
- Thanks,
- Dustin
- +------------------------------------------------+
- Dustin M. Smith
- internet email: dms625s@nic.smsu.edu
- dms625s@vma.smsu.edu
- +------------------------------------------------+
- From news@bigblue.oit.unc.edu Sat Apr 23 03:09:48 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA28711; Sat, 23 Apr 1994 08:44:34 -0400
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA28246; Sat, 23 Apr 1994 07:36:37 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: Sat, 23 Apr 1994 03:09:48 GMT
- From: jones@cbdb1.nimh.nih.gov (Doug Jones)
- Message-Id: <jones.23.00162A83@cbdb1.nimh.nih.gov>
- Organization: CBDB/NIMH/NIH
- Sender: ses
- References: <2p6d73$7vo@nntp2.Stanford.EDU>, <jones.21.000393BD@cbdb1.nimh.nih.gov>, <2p8ckl$lr5@crl2.crl.com>
- Subject: Re: Is it worth trying out the TCP/IP betas?
-
- In article <2p8ckl$lr5@crl2.crl.com> cgi@crl.com (Paul Smith) writes:
- >Is there a timer / expiration date in the Vxb TCP beta stack from Microsoft??
- >There was a rumor about the 1st beta cessing to work on a prticular date
- >several weeks ago??
-
- Here's the quote from the README.TXT distributed with mtcpb2.exe
- by Microsoft:
-
- "This product is compatible with, and supported exclusively on the
- Microsoft Windows for Workgroups 3.11 platform. This beta release expires
- on June 15, 1994. Once it expires, you will be reminded to upgrade to a
- new version every time you run Windows for Workgroups (although the
- software will continue to function properly)."
-
- It doesn't seem to me that it's going to be anything more than a reminder to
- upgrade to something better - just as they state. (I don't think there's any
- sinister " the first one's free, then you'll have to pay" plot afoot here).
- Doug
- jones@cbdb1.nimh.nih.gov
-
-
-
-